Skip to content

refactor: route REST v1 through tuning - #53

Open
sebawebber wants to merge 1 commit into
codex/issue-44-tuning-boundaryfrom
codex/issue-48-rest-v1-shared-tuning
Open

refactor: route REST v1 through tuning#53
sebawebber wants to merge 1 commit into
codex/issue-44-tuning-boundaryfrom
codex/issue-48-rest-v1-shared-tuning

Conversation

@sebawebber

Copy link
Copy Markdown
Contributor

Summary

  • route REST v1 through the shared tuning boundary
  • preserve legacy responses, validation, formats, and documentation
  • retain compatibility behavior for noncanonical historical inputs

Test plan

  • make test
  • Standards review: no findings
  • Spec review: no findings

Stack

Closes #48

Use the shared tuning boundary so REST and newer consumers share one
calculation entry point.

Regression coverage protects the established REST contract during the
migration.

Signed-off-by: Sebastian Webber <sebastian@swebber.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant